-
Notifications
You must be signed in to change notification settings - Fork 603
✨ Addons: Add functionality for resolveConflicts: PRESERVE #5330
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
Welcome @edmondceausu! |
Hi @edmondceausu. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
/ok-to-test |
b599143
to
ef40f66
Compare
Thanks for this! Overall, this looks good to me. The tests are currently failing because Once those are fixed (and it passes e2es), I think we're good! |
/retest |
/test pull-cluster-api-provider-aws-test |
/test pull-cluster-api-provider-aws-e2e |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for this @edmondceausu . Just the one small comment.
|
||
// AddonResolutionPreserve indicates that if there are parameter conflicts then | ||
// resolution will result in preserving the existing value | ||
AddonResolutionPreserve = AddonResolution("preserve") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
New changes should only be added to the latest API types only (i.e. v1beta2
). Can you remove this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Removed
924b7be
to
925b5d4
Compare
/test pull-cluster-api-provider-aws-e2e |
1 similar comment
/test pull-cluster-api-provider-aws-e2e |
/test ? |
New changes are detected. LGTM label has been removed. |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Forgot to update the addons struct kubebuilder to enable access to the preserve function |
/test pull-cluster-api-provider-aws-e2e |
/retest |
21e6453
to
e05c71b
Compare
e05c71b
to
925b5d4
Compare
925b5d4
to
dae829a
Compare
/test pull-cluster-api-provider-aws-e2e |
/retest |
/test pull-cluster-api-provider-aws-e2e-eks |
/label tide/merge-method-squash |
docs/book/src/topics/eks/addons.md
Outdated
preserve | ||
``` | ||
|
||
_Note_: For `conflictResolution` `none` is the **default** behaviour. That means, if not otherwise specified, it's |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm a little confused - it looks like the GoDoc and YAML previously stated that the default was none
, but that was incorrect according to the actual kubebuilder validation rule. The book documentation was correct, though, and this particular change changes that.
Am I missing something in my reading?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You are correct. I had updated the docs on my first review of the feature, but later updated the behavior to reflect what was in the kubebuilder validation rule. I restored the book doc to reflect what is in kubebuilder
fixes for test to pass removed v1beta1 support
e39ec75
to
820ee87
Compare
What type of PR is this?
/kind feature
What this PR does / why we need it:
Added support for resolveConflicts.PRESERVE (API Reference). This is helpful if users are migrating an existing cluster to Cluster API and do not have their existing Addon Configs specified, or if an out of band change is made to an Addon (eg. configMap change) and the user wants to preserve it.
The schema for conflictResolution had listed
none
as the default behavior. I updated the docs and code to reflect that.*
Special notes for your reviewer*:
Checklist:
Release note: